Handle duplicate bin names

The persistent yard model allows duplicate section names. Some sites rely on duplicate section names, for example, to accommodate wheeled work flows. When you use Yard Editor to upgrade your yard model, you can choose to be alerted to duplicate yard section names by adjusting the YRDCORE001 (ALLOW_DUP_BIN_NAME_FOR_YARD_SECTIONS) (on page 1) setting.

When YRDCORE001 is set to:

TRUE (default), N4 tolerates duplicate section names and alerts you to duplicate stack names.

You must resolve duplicate stack names before you can apply the yard model to the active yard, but you may keep duplicate section names.

FALSE, N4 tolerates duplicate section names in non-active yard models but alerts you to duplicate names on both the section- and stack-level. For example:

Name AB01 of Yard section with row index 1 of block ABB conflicts with Yard section with row index 1 of block AB.

You must resolve any duplicate names before you can apply the yard model to the active yard.

If terminals with multiple facilities want to allow duplicate sections at one yard but not at another, they can override the setting at the facility scope level by logging in to each facility.

When validating for duplicate bin names, N4 validates that:

Two different yard stacks do not have the same name.
Two different yard stacks do not have the same alternate name.
The name of a yard stack is not the same as an alternate name of another yard stack.

A single yard stack can have the same value as the name and alternate name.

The following table describes the scenarios in which N4 validates the section and stack bin names, depending on YRDCORE001, along with the steps to take to resolve duplicates.

Scenario	Setting TRUE	Setting FALSE	To Resolve Duplicate Names
Applying yard model changes	N4 validates all stack bin names in the yard model to be applied. If N4 encounters any duplicate stack names, the process stops. The process does not stop if N4 encounters only duplicate section names.	N4 validates all stack and section bin names in the yard model to be applied. If N4 encounters any duplicate stack or section names, the process stops.	Modify the block naming scheme for the related block and bin name tables.
Upgrading the yard	As part of the automated upgrade actions, N4 converts the existing yard's compiled yard file to the persistent bin model. If N4 encounters duplicate stack names, it stops the process and continues with the next upgrade action. When all N4 nodes are started, the yard model exists, but it is not active because of duplicate stack bin names.	As part of the automated upgrade actions, N4 converts the existing yard's compiled yard file to the persistent bin model. If N4 encounters duplicate stack or section bin names, it stops the process and continues with the next upgrade action. When all N4 nodes are started, the yard model exists, but it is not active because of duplicate bin names.	After upgrading, always verify the apex logs and look for duplicate yard stack or section errors. Then do the following: Eliminate duplicate bin names in the yard source file. Create a new yard model (on page 1). Import the modified yard file (on page 1). When prompted to reset geometries, click No. Select Actions Apply Yard Model Changes (on page 1). When the process finishes without errors, verify in the Yard Models view (on page 1) that the yard model is active.

Scenario

Setting TRUE

Setting FALSE

To Resolve Duplicate Names

Applying yard model changes

N4 validates all stack bin names in the yard model to be applied. If N4 encounters any duplicate stack names, the process stops. The process does not stop if N4 encounters only duplicate section names.

N4 validates all stack and section bin names in the yard model to be applied. If N4 encounters any duplicate stack or section names, the process stops.

Modify the block naming scheme for the related block and bin name tables.

Upgrading the yard

As part of the automated upgrade actions, N4 converts the existing yard's compiled yard file to the persistent bin model. If N4 encounters duplicate stack names, it stops the process and continues with the next upgrade action. When all N4 nodes are started, the yard model exists, but it is not active because of duplicate stack bin names.

As part of the automated upgrade actions, N4 converts the existing yard's compiled yard file to the persistent bin model. If N4 encounters duplicate stack or section bin names, it stops the process and continues with the next upgrade action. When all N4 nodes are started, the yard model exists, but it is not active because of duplicate bin names.

After upgrading, always verify the apex logs and look for duplicate yard stack or section errors. Then do the following:

Eliminate duplicate bin names in the yard source file.
Create a new yard model (on page 1).
Import the modified yard file (on page 1).
When prompted to reset geometries, click No.
Select Actions Apply Yard Model Changes (on page 1).
When the process finishes without errors, verify in the Yard Models view (on page 1) that the yard model is active.